Internal Name:

Deployment

Description:

Singleton:

no

Plugin:

JBossAS7

Path

yes

path

Status

trait

The current runtime status of a deployment. Possible status modes are OK, FAILED, and STOPPED. FAILED indicates a dependency is missing or a service could not start. STOPPED indicates that the deployment was manually stopped.

status

Content

List of pieces of content that comprise the deployment.

yes

content

Enabled

Boolean indicating whether the deployment content is currently deployed in the runtime (or should be deployed in the runtime the next time the server starts.)

yes

enabled

Name

Unique identifier of the deployment. Must be unique across all deployments.

yes

name

Persistent

Boolean indicating whether the existence of the deployment should be recorded in the persistent server configuration. Only relevant to a standalone mode server. Default is 'true'. A deployment managed by a deployment scanner would have this set to 'false' to ensure the deployment is only deployed at server start if the scanner again detects the deployment.

yes

persistent

Runtime Name

Name by which the deployment should be known within a server runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as 'name', but in some cases users may wish to have two deployments with the same runtime-name (e.g. two versions of foo.war) both available in the deployment content repository, in which case the deployments would need to have distinct name; values but would have the same runtime-name.

yes

runtime-name

Enable

Disable

Restart

File

Deployable